🔗 Linked issue

No open issue related to Dutch translations.

🧭 Context

Dutch language contains incorrect and missing translations.

📚 Description

All translations were reviewed and manually tested in a local environment.

• Some keys were incorrectly translated in a sentence. For example, "affiliëerd" should be "geaffilieerd"
• Some keys were wrongly typed. For example, "geregisteerd" should be "geregistreerd"
• Some keys were using English term. For example, "trademark" instead of "handelsmerk"
• Mix of informal and formal pronouns (u/jij) was used. Majority of existing translations uses formal style and so I opted for a consistent formal style of pronouns.
• Mixed pronouns were used (u/uw, je/jij). The majority of usage is formal, so I opted for the formal pronouns usage
• Translated missing keys listed in the "translation status" for the Dutch language
• Some translations (across multiple languages in fact) use "ChatGPT-style" title capatalization, where each word starts with a capital letter. Since styles are mixed, I removed the "ChatGPT-style" capatalization for some keys
• English translations referred to "the repository", while Dutch translation used "een repository". I aligned the Dutch translation with the English version for consistency.
• Replaced "Wijzigingenoverzicht" with "Changelog" because I believe it is more clear to the target audience of this app. Although it is an English term, it is commonly used in technical discussions within the Netherlands. This is subjective change and chan be reverted if preferred.
• I translated "stats" to "statistieken" where appropriate. However, I kept "stats" in the navigation menu because space is more limited and the term is common to the target audience (even if it's a non-Dutch term). This is also a subjective choice and can be adjusted if necessary.